home *** CD-ROM | disk | FTP | other *** search
- Hints for ShroudIt!
- flflflflflflflflflflflflflflflflflflfl
-
- Here are a few quick hints to guide you getting started with ShroudIt!
- Of course you are eventually going to have to read the manual, SHROUDIT.DOC
- but for now here's a road test guide:
-
- 1) Review the keywords file (.KEY), if you are using an extended language
- set, make sure you include the function names here. If you don't your
- compiler is going to complain about UNKNOWN function name. When
- this happens check the .MAP file to see the actual name for the
- shrouded symbol, and add it back in to the .KEY file.
-
- 2) If you are using a toolkit, GUI, SQL, communications, and so forth,
- add these function names to the global functions (.GLB) file.
-
- Try and avoid putting globals in the keyword list, of course this
- will still work, but it can be a maintenance nightmare...
-
- 3) Pick a file initially without a lot of complex includes. These can
- require a lot of planning and adjusting on your part to decide which
- names are global, local, and therefore do or do not need entries in
- the .GLB file.
-
- 4) If there are global names you want to shroud, but must always be
- unique, you can force this in .GLB by using: My_Global, XT_SAQWEJ
- this tells ShroudIt! to use the mapping name you specify instead.
-
- 5) Don't think that Shrouding is a quick, just run it and its done
- process. It does take time to tune everything as you need it.
- The best analogy I can think of is like trying to compile Borland
- C code using Microsoft C. Except here you are adjusting the
- ShroudIt! parameters to match, instead of fiddling the actual code.
-
- 6) Unpack and review the example control file sets provided. You
- will find the following .ZIP files available:
-
- COBOL.ZIP
- PROLOG.ZIP
- BASIC.ZIP
- DBASE.ZIP
- PERL.ZIP
- EXAMPLES.ZIP
-
- Each one is designed to give you a head start on using a particular
- language. You should tailor them to match your own code usage.
-
-